File access with different file hosts

ABSTRACT

A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 14/323,841 filed Jul. 3, 2014, which is acontinuation of and claims priority to U.S. patent application Ser. No.13/117,598 filed May 27, 2011, the disclosures of which are incorporatedby reference herein in their entirety.

BACKGROUND

Users oftentimes have a variety of different files of interest to them,such as document files, image files, music files, video files, and soforth. These files can be stored on various storage devices, such as ona hard drive of the user's computer or on a server over a network.Tracking these files across such storage devices, however, can becumbersome on the user, oftentimes requiring the user to access thosevarious storage devices from each application with which he or shedesires to use the files and keep track of which storage devices havewhich files.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

In accordance with one or more aspects, a file access request isreceived from an application. One or more file types for the file accessrequest are identified, and one or more file hosts supporting files ofthe identified one or more file types are also identified. A userinterface is displayed, the user interface including a hosted area.Within the hosted area, at least one of the one or more file hostsdisplays a portion of the user interface identifying one or more filesof the at least one file host that can be selected for retrieval.

In accordance with one or more aspects, a file access request isreceived from an application. A file type of a file to be saved by theapplication is identified, and one or more file hosts supporting filesof the identified file type are also identified. A user interface isdisplayed, the user interface including a hosted area. Within the hostedarea, at least one of the one or more file hosts displays a portion ofthe user interface allowing the file to be saved by the at least onefile host.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.

FIG. 1 illustrates an example system implementing the file access withdifferent file hosts techniques discussed herein in accordance with oneor more embodiments.

FIG. 2 illustrates another example system implementing the file accesswith different file hosts techniques discussed herein in accordance withone or more embodiments.

FIGS. 3, 4, 5, and 6 each depict an example user interface displayedusing the file access with different hosts techniques discussed hereinin accordance with one or more embodiments.

FIG. 7 illustrates an example procedure for implementing the file accesswith different file hosts in accordance with one or more embodiments.

FIG. 8 illustrates another example procedure for implementing the fileaccess with different file hosts in accordance with one or moreembodiments.

DETAILED DESCRIPTION

Overview

File access with different file hosts is discussed herein. When using anapplication, a user can retrieve files maintained by various file hosts,such as file systems, other applications, service providers, and soforth. Similarly, a user can save files to various file hosts. A userinterface (UI) having a hosted area is displayed, and various file hostscan display a user interface within the hosted area. Each file host cantailor the display within the hosted area as the file host desires. Byinteracting with the user interface displayed in this hosted area, theuser can select files from the various file hosts for retrieval into theapplication he or she is using, and/or select a destination file host towhich a file is to be saved.

In the following discussion, an example system is first described thatis operable to perform techniques described herein. Example proceduresare then described, which are operable in the example system as well asin other systems. Likewise, the example system is not limited toperformance of the example procedures.

Example System

FIG. 1 illustrates an example system 100 implementing the file accesswith different file hosts techniques discussed herein in accordance withone or more embodiments. The illustrated system 100 includes a computingdevice 102, which may be configured in a variety of ways. For example,computing device 102 can be configured as a computer that is capable ofcommunicating over a network 104, such as a desktop computer, a tabletor notepad computer, a mobile station, an entertainment appliance, aset-top box communicatively coupled to a display device, a television orother display device, a cellular or other wireless phone, a gameconsole, and so forth.

Computing device 102 may range from a full resource device withsubstantial memory and processor resources (e.g., personal computers,game consoles) to a low-resource device with limited memory and/orprocessing resources (e.g., traditional set-top boxes, hand-held gameconsoles). Additionally, although a single computing device 102 isshown, computing device 102 may be representative of multiple differentdevices, such as multiple servers utilized by a business to performoperations, a remote control and set-top box combination, an imagecapture device (e.g., camera) and a game console configured to capturegestures, and so on.

Computing device 102 can also include an entity (e.g., software) thatcauses hardware of the computing device 102 to perform operations, e.g.,configures processors, functional blocks, and so on. For example,computing device 102 may include a computer-readable medium that may beconfigured to maintain instructions that cause the computing device, andmore particularly hardware of computing device 102 to performoperations. Thus, the instructions function to configure the hardware toperform the operations and in this way result in transformation of thehardware to perform the operations. The instructions may be provided bythe computer-readable medium to computing device 102 through a varietyof different configurations.

One such configuration of a computer-readable medium is signal bearingmedium and thus is configured to transmit the instructions (e.g., as acarrier wave) to the hardware of the computing device, such as vianetwork 104. The computer-readable medium may also be configured as acomputer-readable storage medium and thus is not a signal bearingmedium. Examples of a computer-readable storage medium include arandom-access memory (RAM), read-only memory (ROM), optical discs (e.g.,DVD or CD), flash memory, hard disk memory, and other memory devicesthat may use magnetic, optical, and other techniques to storeinstructions and other data.

Network 104 can assume a variety of different configurations. Forexample, network 104 can include the Internet, a wide area network(WAN), a local area network (LAN), a personal area network (PAN), awireless network, a public telephone network, an intranet, combinationsthereof, and so on. Further, although a single network 104 is shown,network 104 may be configured to include multiple networks.

Computing device 102 is illustrated as including a file managementmodule 106. File management module 106 is representative offunctionality to manage access to one or more files, including files ina file system 108. File management module 106 can be implemented in avariety of ways, such as a stand-alone application, as part of anoperating system of computing device 102, as an application thatexecutes in conjunction with the operating system, and so on.

File system 108 employs techniques to organize and store files 110 bycomputing device 102. File system 108, for instance, can employ ahierarchy of folders to manage files 110 (e.g., executable and/orlibrary files) in storage. A variety of other file management techniquesthat may be employed by file management module 106 and file system 108are contemplated. Additionally, a variety of different types of files110 can be managed using file management module 106. For example, files110 can be text (document) files, image files, video files, audio files,combinations thereof, and so forth.

An application 112 is one or more programs, scripts, or othercollections of instructions that run on computing device 102.Application 112 can assume a variety of different configurations, suchas an entertainment application (e.g., a game or audio/video player), autility application (e.g., a word processor or Web browser), a referenceapplication (e.g., a dictionary or encyclopedia), and so forth.Application 112 can be one or more programs, scripts, or othercollections of instructions that run on computing device 102 and can bestored as files 110. Alternatively, application 112 can be one or moreprograms, scripts, or other collections of instructions that aredownloaded from a remote service (e.g., via network 104) and run oncomputing device 102 without being stored as files 110. Or, application112 can be one or more programs, scripts, or other collections ofinstructions that are run on a remote service, with a user interfacegenerated by the remote service and provided (e.g., via network 104) tocomputing device 102 for display, and inputs received at computingdevice 102 being returned (e.g., via network 104) to the remote servicefor processing.

In one or more embodiments, application 112 is an isolated application,being run in a manner in which the ability of application 112 to accessresources (e.g., networked computers, the Internet, modules, devices,memory, other applications) of computing device 102 is restricted. Theoperating system (and/or other software, firmware, and/or hardware) ofcomputing device 102 allows an isolated application to access memory andother resources of computing device 102 that have been allocated orotherwise made available to the isolated application, but prevents theisolated application from accessing other memory of, resources of,and/or applications running on computing device 102. This protects otherapplications running on computing device 102 from being interfered withby the isolated application, as well as protects the isolatedapplication from being interfered with by other applications running oncomputing device 102, thus isolating the application from otherapplications on computing device 102.

In one or more embodiments, application 112 is run in a restrictedmanner by being run in a sandbox. Although a single application 112 isillustrated in computing device 102, it should be noted that multipleapplications can be running in computing device 102 concurrently (eachapplication being executed in its own sandbox).

File management module 106 is further illustrated as including a brokermodule 114 and a picker module 116. Broker module 114 is representativeof functionality of file management module 106 to manage access ofapplication 112 to various file hosts, such as file system 108, otherapplications, service providers, and so forth. Broker module 114, forinstance, may act as an intermediary to locate files requested byapplication 112 and provide those files back to application 112.Further, such files may be provided to application 112 and application112 need not be aware of where the files were obtained (e.g., thenamespace used by file system 108, the host, and so forth). For example,broker module 114 can operate as an abstraction layer that isolatesapplication 112 from specific details regarding various file hosts andthe manner in which those file hosts store files.

Additionally, broker module 114 may employ picker module 116 toconfigure a user interface such that a user may select files fromvarious file hosts. Picker module 116 includes a UI module 122 managingcommunication with file hosts as appropriate, including managing remoteaccess (e.g., with service provider 120 over network 104). UI module 122also manages at least a portion of a user interface based oncommunications with other file hosts. For example, UI module 122 canconfigure a portion of a user interface such that a user can selectremote files that are accessible via a service provider 120 (e.g.,implemented using one or more computing devices) over network 104,select remote files that are managed by an application of serviceprovider 120, select files that are managed by other applications oncomputing device 102, and so forth.

Various modules and applications of computing device 102, such asapplication 112 and picker module 116, can receive user inputs from auser of computing device 102. These user inputs can provide data, userselections, and so forth. User inputs can be provided in a variety ofdifferent manners, such as by pressing one or more keys of a keypad orkeyboard of device 102, pressing one or more keys of a controller (e.g.,remote control device, mouse, trackpad, etc.) of device 102, pressing aparticular portion of a touchpad or touchscreen of device 102, making aparticular gesture on a touchpad or touchscreen of device 102, and/ormaking a particular gesture on a controller (e.g., remote controldevice, mouse, trackpad, etc.) of device 102. User inputs can also beprovided via other physical feedback input to device 102, such astapping any portion of device 102, an action that can be recognized by amotion detection component of device 102 (such as shaking device 102,rotating device 102, etc.), and so forth. User inputs can also beprovided in other manners, such as via audible inputs to a microphone,via motions of hands or other body parts observed by an image capturedevice, and so forth.

Generally, any of the functions described herein can be implementedusing software, firmware, hardware (e.g., fixed logic circuitry), manualprocessing, or a combination of these implementations. The terms“module” and “functionality” as used herein generally representhardware, software, firmware, or a combination thereof. In the case of asoftware implementation, the module, functionality, or logic representsinstructions and hardware that performs operations specified by thehardware, e.g., one or more processors and/or functional blocks.

FIG. 2 illustrates an example system 200 implementing the file accesswith different file hosts techniques discussed herein in accordance withone or more embodiments. System 200 as illustrated may be implemented inpart by file management module 106 of computing device 102 of FIG. 1 toperform file management techniques.

System 200 as illustrated includes application 202 (which can be, forexample, an application 112 of FIG. 1), a broker module 114, a pickermodule 116, and one or more file hosts 204. In this example, application202 communicates with broker module 114 via one or more applicationprogramming interfaces (APIs) exposed by broker module 114 to accessfile hosts 204. Although a single application 202 and particular fileshosts 204 are illustrated in FIG. 2, it should be noted that system 200can include any number of applications 202 accessing any number of filehosts 204.

In one or more embodiments, application 202 is permitted to access filehosts 204 without being aware of where and/or how particular files arearranged, organized, maintained, and so forth by file hosts 204.Application 202, for instance, may be unaware of a namespace or datamodel used to access files by file hosts 204. Therefore, broker module114 may convert requests from application 202 received via the APIs intoa form that is understandable to locate files of interest.

In other embodiments, application 202 may be made aware of where and/orhow files are arranged and located within particular file hosts 204. Forinstance, application 202 may be configured to use a namespace supportedby local file system 212 such that conversion of the request is notperformed by broker module 114. A variety of other examples are alsocontemplated, such as to enable direct access to local file system 212without interacting with broker module 114 for particular applications(in which case files can be accessed via other user interfaces otherthan user interface 206 discussed below).

Picker module 116 presents a user interface 206 facilitating userselection of files for retrieval and/or destinations for saving files.User interface 206 allows files to be retrieved from and/or saved tovarious file hosts. For example, user interface 206 can include a hostedarea in which a user interface generated by a file host 204 isdisplayed.

Broker module 114 and picker module 116 act as intermediaries betweenapplication 202 and file hosts 204. Applications 202 may be unaware offile hosts 204, and file hosts may be unaware of application 202.Additionally, user interface 206, including the hosted area in whichfile hosts 204 can display a portion of the user interface, is providedby picker module 116. Thus, application 202 may be unaware of theparticular file host displaying a user interface in the hosted portionat any given time, as well as be unaware of the particular file host 204from which files are accessed (e.g., which file host 204 files areretrieved from or saved to).

Broker module 114 and/or picker module 116 can communicate with variousdifferent file hosts 204, such as local file system 212, application214, remote file system 216, and service provider 218. Broker module 114and/or picker module 116 can communicate with file hosts 204 indifferent manners, and in one or more embodiments modules 114 and/or 116are configured with (or can otherwise obtain) information indicating howto communicate with each of the file hosts 204.

A file host 204 refers to a system, service, application, and so forththat organizes, manages, and/or stores files. A file host 204 candisplay a user interface in a hosted area, allowing files of the filehost (files that the file host organizes, manages, and/or stores) to beaccessed (e.g., retrieved, stored, and so forth). A file host 204 canorganize and store files in various different manners using variousdifferent data models (the format and/or protocol used in storingfiles), such as storing files as individual files on a storage device,as files in a database or other record, as part of grouping orcollection of files (e.g., as part of a zip or cabinet file), and soforth. Regardless of the data model used by file hosts 204, each filehost 204 is aware of how to access (e.g., identify, store, retrieve,modify) the files that that file host 204 organizes, manages, and/orstores.

Local file system 212 is a file host that stores files 222 in one ormore folders on local storage devices that are part of or connected tothe computing device running application 202, including removablestorage devices. Local file system 212 can, for example, store files 222on local hard disks, optical discs, Flash memory devices, or othercomputer-readable storage media.

Remote file system 216 is a file host that stores files 226 in one ormore folders on a remote storage device that is not the same computingdevice as is running application 202. For example, the remote storagedevice can be coupled to the computing device running application 202via network 104 of FIG. 1. Remote file system 216 can store files onvarious different computer-readable storage media, analogous to localfile system 212.

Application 214 can assume a variety of different configurations, andcan be one or more programs, scripts, or other collections ofinstructions run on various devices, analogous to application 112 ofFIG. 1. Application 214 can also be an isolated application, analogousto application 112 of FIG. 1. Application 214 is typically running onthe same computing device as application 202, although can alternativelybe running on another computing device. Application 214 is a file hostthat stores files 224 in various manners. Application 214 can leveragelocal file system 212 and/or remote file system 216 to store files 224,but files 224 are typically accessible only through application 214.

Service provider 218 is one or more applications that can assume avariety of different configurations, providing various services toapplication 202 such as photo management services, social networkingservices, messaging or other communication services, document editingservices, and so forth. Service provider 218 includes one or moreapplications that are typically running on one or more differentcomputing devices than application 202, such as on one or more computingdevices coupled to the computing device running application 202 vianetwork 104 of FIG. 1. Service provider 218 is a file host that storesfiles 228 in various manners. Service provider 218 can leverage localfile system 212 and/or remote file system 216 to store files 228, butfiles 228 are typically accessible only through service provider 218.

When application 202 desires to access a file host, such as to allow auser of application 202 to select one or more files for retrieval intoapplication 202 or save one or more files from application 202,application 202 communicates a file access request to broker module 114.Because application 202 is making the file access request, application202 is also referred to as the calling application. The file accessrequest is communicated, for example, by invoking an API of brokermodule 114. In response to the file access request, broker module 114invokes picker module 116, which displays user interface 206.Alternatively, application 202 can bypass broker module 114 andcommunicate a file access request to picker module 116, invoking pickermodule 116 directly to display user interface 206 without going throughbroker module 114.

User interface 206 includes a hosted area, which is a portion of theuser interface in which one or more file hosts 204 can display a userinterface. The user interface displayed within the hosted area isgenerated by a file host 204. An application 214 or service provider 218displaying a user interface within the hosted area can also be referredto as a hosting application. Each file host 204 can tailor the displaywithin the hosted area as that file host 204 desires, optionallymodifying and changing that display over time as that file host 204desires. Application 202 can be unaware of (and have no knowledge of)the manner in which the user interface displayed within the hosted areais generated, the data model or namespace used by the file host 204, andso forth. Similarly, picker module picker module 116 can be unaware of(and have no knowledge of) the manner in which the user interfacedisplayed within the hosted area is generated, the data model ornamespace used by the file host 204, and so forth.

Picker module 116 (e.g., UI module 122 of picker module 116) providesthe hosted area in which one or more file hosts 204 can display a userinterface. The hosted area can be, for example, a window in which theuser interface of a file host 204 can be displayed or otherwisepresented. The user interface can be displayed within the hosted area indifferent manners. For example, the user interface to be displayedwithin the hosted area can be received from a file host 204 anddisplayed by picker module 116. By way of another example, the file host204 can be allowed to directly display the user interface in the hostedarea (e.g., in a particular window). However, regardless of the mannerin which the user interface is displayed within the hosted area, theuser interface of the file host is restricted to that host area. Theuser interface of the file host is not permitted to overwrite otherareas of the UI not within the hosted area, and is not permitted topreempt the UI provided by the operating system of the computing deviceor other applications running on the computing device.

It should be noted that, as picker module 116 provides the hosted areain which one or more file hosts 204 can display a user interface, thehosted area is not provided by a plug-in or extension code incorporatedinto application 202. In addition to being unaware of (and having noknowledge of) the manner in which the user interface displayed withinthe hosted area is generated, application 202 can be unaware of theparticular file host generating the user interface displayed within thehosted area. The particular file host generating the user interfacedisplayed within the hosted area, as well as the file hosts 204available to generate the user interface displayed within the hostedarea, can change without application 202 being aware of the changes.

User interface 206 can display a single hosted area in which a singlefile host 204 can display a user interface at a time, and the file host204 displaying a user interface within the hosted area can change overtime. Alternatively, user interface 206 can display multiple hostedareas concurrently, allowing multiple file hosts 204 to display userinterfaces concurrently.

Picker module 116 can identify a file host 204 to display a userinterface within the hosted area in different manners. In one or moreembodiments, identifiers of various file hosts 204 are presented as partof user interface 206, such as in a file host identification portion ofuser interface 206. A user input selecting one of the identifiers isreceived, and picker module 116 invokes the file host 204 having theselected identifier to display a user interface within the hosted area.Alternatively, picker module 116 can identify a file host 204 to displaya user interface within the hosted area in other manners, such as byidentifying a default file host (e.g., that picker module 116 isconfigured with or can otherwise identify), selecting a file hostrandomly or according to other rules or criteria, identifying a filehost based on a preference or configuration setting received from a userof system 200, and so forth.

The file hosts 204 available in system 200 can be determined indifferent manners. In one or more embodiments, each file host 204 isregistered as being a file host 204 for picker module 116. As part of aregistration process, various information regarding file host 204 isprovided, such as how to activate the file host 204, file typessupported by the file host, and so forth. This registration can beperformed at various times, such as when the file host is installed on acomputing device implementing picker module 116, when the file hostaccesses a computing device implementing picker module 116, in responseto a user request, and so forth. When determining the file hosts 204available in system 200 (e.g., and thus the file hosts 204 for whichidentifiers are to be displayed within a file host identificationportion of user interface 206), picker module 116 can identify onlythose file hosts that have registered as being a file host 204 forpicker module 116.

Alternatively, the file hosts 204 available in system 200 can beidentified in different manners. For example, a remote service can beaccessed (e.g., via network 104 of FIG. 1) to identify servicescurrently accessible by the computing device running application 202,and those identified services can be file hosts 204. By way of anotherexample, a list of file hosts from a vendor or administrator of thecomputing device running application 202 can be accessed to determinethe file hosts 204 available in system 200.

Additionally, in one or more embodiments file hosts 204 can supportdifferent file types. A file type refers to a particular type of datastored in the file and/or format in which data is stored in a file. Forexample, file types can be images files, audio files, video files, textfiles, and so forth. By way of another example, file types can be JPEG(Joint Photographic Experts Group) files, PDF (Portable Document Format)files, and so forth. A file type being supported by a file host 204refers to the file host 204 organizing, managing, and/or storing fileshaving that file type. The file types supported by each file host 204are identified, such as during the registration process discussed above.As part of a file access request, application 202 can identify one ormore file types that application 202 desires for that file accessrequest. Picker module 116 identifies (e.g., as file hosts 204 for whichidentifiers are to be displayed within a file host identificationportion of user interface 206) only those file hosts that support thefile type requested by application 202. Thus, a file host 204 that doesnot support a file type requested by application 202 is not identifiedas a file host that can display a user interface within the hosted area.However, if a subsequent access request from application 202 is receivedfor another file type that is supported by that file host 204, then thatfile host 204 is identified as a file host that can display a userinterface within the hosted area.

When a file host 204 is identified as the file host 204 to display auser interface within the hosted area, the identified file host 204 isactivated or otherwise invoked by picker module 116. Picker module 116is aware of, or can obtain, information indicating how to activate orinvoke a file host 204. This information can be obtained, for example,as part of a registration process as discussed above. If the file host204 is not already running then picker module 116 activates or launchesthe file host 204, invoking the file host 204 to display a userinterface within the hosted area. If the file host 204 is alreadyrunning, then picker module 116 invokes the file host 204 to display auser interface within the hosted area.

The activated or invoked file host 204 displays the user interface inthe hosted area in various manners as determined by the file host 204itself. Files can be displayed with different representations, such asicons, video sequences, text descriptions, and so forth. Data can beinput by a user in different manners, such as via a text entry field,via gestures, audibly, and so forth.

The user interface displayed by the file host 204 in the hosted area canallow various accesses to files managed by the file host 204. Forexample, the user interface can allow navigating through folders orother groupings of files, selecting one or more files for retrieval,selecting one or more locations for saving a file, and so forth.

In situations in which the file access request from application 202 isrequesting to retrieve one or more files, the user interface displayedby the file host 204 identifies (e.g., displays icons or thumbnailsrepresenting) one or more files of each of one or more file hosts 204from which the user of application 202 can select. The selection can bemade by the user providing a variety of different inputs as discussedabove. Upon selection of one or more files (from one or more file hosts204), the one or more file hosts 204 provide the selected one or morefiles (or an indication of where and/or how to retrieve the one or moreselected files) to picker module 116. Picker module 116 provides the oneor more selected files (or an indication of where and/or how to retrievethe one or more selected files) to broker module 114. Broker module 114returns to application 202 the one or more selected files (oralternatively an indication of where and/or how application 202 canretrieve the selected one or more files or the content of the one ormore files).

In situations in which the file access request from application 202 isrequesting to save or store one or more files, the user interfacedisplayed by the file host 204 identifies (e.g., displays icons orthumbnails representing) one or more locations of the file host 204 fromwhich the user of application 202 can select. The user interfacedisplayed by the file host 204 can also provide a user input portionallowing the user to provide various information regarding the one ormore files (e.g., names of the one or more files, descriptions of theone or more files). As part of the file access request to save or storea file, application 202 can optionally provide information identifyingthe file. This information can be provided to the file host 204displaying the user interface in the hosted area, allowing the file host204 to incorporate information regarding the file to be saved in theuser interface in the hosted area. For example, application 202 canprovide to the file host 204 (via broker module 114 and picker module116) a thumbnail or icon representing the file to be saved. The filehost 204 can display this thumbnail or icon as part of the userinterface in the hosted area.

Application 202 provides the one or more files to be saved (or anindication of where and/or how to obtain the one or more files to besaved) to broker module 114. Broker module 114 provides the one or morefiles to be saved (or an indication of where and/or how to obtain theone or more files to be saved) to picker module 116, which provides theone or more files to be saved (or an indication of where and/or how toobtain the one or more files to be saved) to the file host 204displaying the user interface in the hosted area. Upon receiving a userselection of a location to store the one or more files, the file host204 displaying the user interface in the hosted area stores the one ormore files in the selected location (and optionally with the additionalprovided information regarding the one or more files). Application 202can provide the one or more files to be saved (or an indication of whereand/or how to obtain the one or more files to be saved) as part of thefile access request, or alternatively at other times (e.g., in responseto a request for the one or more files from picker module 116, therequest provided by picker module 116 in response to a user selection ofa location where the one or more files are to be saved).

In system 200, application 202 is a calling application providing accessrequests to broker module 114, and application 214 is a hostingapplication that can provide a user interface in a hosted area of userinterface 206. However, it should be noted that an application can be ahosting application and/or a calling application at the same and/ordifferent times. For example, application 202 can be a social networkingapplication and application 214 can be a photo editing application. Thesocial networking application can be the hosted application and thephoto editing application can be the calling application at one point intime allowing images to be retrieved from the social networkingapplication into the photo editing application, and at a later point intime the photo editing application can be the hosted application and thesocial networking application can be the calling application allowingimages to be retrieved from the photo editing application into thesocial networking application. Continuing with this example, while thephoto editing application is the calling application with respect to thesocial networking application, a word processing application can be acalling application and the photo editing application can be a hostapplication for the word processing application, thus allowing images tobe retrieved from the photo editing application into the word processingapplication concurrently with allowing images to be retrieved from thesocial networking application into the photo editing application.

The file access with different file hosts techniques discussed hereinsupport various usage scenarios. For example, while using a particularapplication, a user is able to request that files of a particular type(e.g., pictures) be retrieved into that one application. Various otherapplications or service providers that support files of that particulartype can be identified and display user interfaces to the user. The useris able to select one or more files from those various otherapplications, in response to which the selected one or more files areretrieved into the particular application the user is using. The usercan thus easily retrieve into the particular application files fromanother application without having to separately save files from theother application onto a storage device, and then retrieve those savedfiles into the particular application. Furthermore, the user canretrieve such files from the other application while the particularapplication into which the files are being retrieved is unaware of thedata model used by the other application (and unaware of the otherapplication itself).

Example User Interfaces

The following section describes example user interfaces that may beimplemented using the previously described systems and devices. Thecomputing device 102, for instance, may output the user interface 206through execution of instructions on hardware of the computing device102, e.g., one or more processors and/or functional blocks that areconfigured to perform operations by the instructions. Although thesetechniques are described for output by the user interface 206 of thepicker module 116, these techniques may be employed by a wide variety ofdifferent user interfaces without departing from the spirit and scopethereof.

FIG. 3 depicts an example implementation 300 of the computing device 102of FIG. 1 configured as a mobile communication device and as outputtinga user interface 302. User interface 302, as discussed above, may beoutput to provide access to files of various file hosts 204.Accordingly, user interface 302 may be configured to support navigationthrough the files of various file hosts 204 in response to user inputssuch that the user may manage how this access is performed.

User interface 302 in this example is illustrated as including anavigation portion 304 including an indication that a file accessrequest to open picture types of files has been received. User interface302 also includes a host identification portion 306, which can bedisplayed for example in response to user selection of the “jump to”option in navigation portion 304. Host identification portion 306displays identifiers of various file hosts 204. In the illustratedexample, host identification portion 306 displays identifiers of:“Computer”, “Desktop”, “Downloads”, “Music”, “Pictures”, “Photo GalleryApp”, and “Social App”. The identifiers of “Computer”, “Desktop”,“Downloads”, “Music”, “Pictures” can refer to different file hosts ordifferent locations of the same file host (e.g., different folders orlibraries in a local file system). The identifier “Photo Gallery App”identifies a file host that is an application (e.g., a photo galleryapplication), and the identifier “Social App” identifies a file hostthat is also an application (e.g., a social networking application). Theidentifiers are listed as text representations, although a variety ofother representations are also contemplated, such as images, icons,video sequences, and so forth.

A user can provide inputs via user interface 302 in a variety ofdifferent manners as discussed above. For example, a user can use his orher hand 308 to touch and thus select the “jump to” option in navigationportion 304 to have host identification portion 306 displayed, or touchand thus select one of the identifiers in host identification portion306 to have files of the file host identified by the selected identifierdisplayed in a hosted area.

Thus, user interface 302 may be output in response to a variety offactors. For example, broker module 114 may receive a file accessrequest from application 112. In response, broker module 114 and/orpicker module 116 may output user interface 302. A variety of otherexamples are also contemplated.

FIG. 4 depicts an example implementation 400 of the computing device 102of FIG. 1 configured as a mobile communication device and as outputtinga user interface 402. User interface 402, as discussed above, may beoutput to identify files of a file host 204 that can be selected by auser. User interface 402 assumes that the “Photo Gallery App” identifierin host identification portion 306 of user interface 302 was selected.Accordingly, user interface 302 may be configured to support navigationthrough the files of the photo gallery application in response to userinputs such that the user may manage how this access is performed.

User interface 402 includes a navigation portion 304, illustrating anidentifier of the photo gallery application (e.g., “Photo Gallery App”)and an up-arrow that can be selected by the user to return to theprevious screen (e.g., user interface 302).

User interface 402 also includes a hosted area 404 in which the photogallery application generates the user interface. In the illustratedexample, the photo gallery application generates a user interface havinga large image on the left-hand side of hosted area 404, and thumbnailsof other images of the photo gallery application on the right-hand sideof hosted area 404. A user can select (e.g., by touching with his or herhand 308) a thumbnail on the right-hand side of hosted area 404 to havethe selected image displayed as a large image on the left-hand side ofhosted area 404. The user can select (e.g., by touching with his or herhand 308) import button 406 to have the file including the large imageon the left-hand side of hosted area 404 returned to the callingapplication. A variety of other user inputs can also be provided toselect the large image on the left-hand side of hosted area 404 asrepresenting the file to be returned to the calling application, such asdouble-clicking or double-tapping the large image, pressing and holdingfor at least a threshold amount of time a thumbnail of the image, and soforth.

FIG. 5 depicts an example implementation 400 of the computing device 102of FIG. 1 configured as a mobile communication device and as outputtinga user interface 502. User interface 502 is similar to user interface402, but includes a collection portion 504 that facilitates selectingmultiple files from one or more different file hosts. Collection portion504 can be provided by, for example, picker module 116. Files can beselected in different manners, such as being double-clicked ordouble-tapped on, being dragged and dropped from the right-hand side ofhosted area 404 to collection portion 504, and so forth. As files areselected, thumbnails of the files are displayed in collection portion504. The user can optionally select files from multiple file hosts, suchas by selecting the up-arrow in navigation portion 304 to return to userinterface 302. The user can then select an identifier of another filesource (e.g., the social networking application represented by “SocialApp” in host identification portion 306), in response to which the userinterface displayed in hosted area 404 is provided by the socialnetworking application. One or more additional files from the socialnetworking application can be selected and added to collection portion504 (in addition to the thumbnails of the files selected from the photogallery application already displayed in collection portion 504).

After the user has selected one or more files, the user can select(e.g., by touching with his or her hand 308) import button 506 to havethe selected one or more files (whose thumbnails are displayed incollection portion 504) returned to the calling application. A varietyof other user inputs can also be provided to have the selected one ormore files returned to the calling application.

FIG. 6 depicts an example implementation 600 of the computing device 102of FIG. 1 as displaying a user interface configured to save files to afile host. In this example, a user interface 602 is configured by thecomputing device 102 to save a file to a photo gallery application filehost. The user interface 602 includes a hosted area 604 in which thephoto gallery application generates a user interface and that includes arepresentation of a file, which is an image in this instance. Arepresentation of a mountain is illustrated as being selected to save tothe file host.

Hosted area 604 also includes a save portion 606 that is configured tospecify information about the file to be saved, which in this instanceis a name “Vacation” and a type of file (a JPEG file). A soft keyboard608 is further displayed as part of hosted area 604, and is configuredto receive touch inputs to enter data into save portion 606. In thisway, a user may navigate through a user interface, specify a file to besaved, enter information that is to be used to save the file (e.g., thetype of the file), and have the file saved through interaction with theuser interface 602.

Example Procedures

The following discussion describes file access with different file hoststechniques that may be implemented using the previously describedsystems and devices. Aspects of each of the procedures may beimplemented in hardware, firmware, software, or a combination thereof.The procedures are shown as a set of acts that specify operationsperformed by one or more devices and are not necessarily limited to theorders shown for performing the operations by the respective acts. Inportions of the following discussion, reference will be made to elementsof FIGS. 1 and 2.

FIG. 7 illustrates an example procedure 700 for implementing the fileaccess with different file hosts in accordance with one or moreembodiments. Procedure 700 is implemented by a file management module,such as file management module 106. In procedure 700, a file accessrequest is received from an application (act 702). The request can bereceived by the application invoking an API exposed by a broker moduleof the file management module, as discussed above, and can be a requestto retrieve one or more files.

One or more file types for the file access request are identified (act704). These one or more file types can be identified as part of the fileaccess request, as discussed above. These one or more file types aretypically the types of files for which the application is requestingretrieval.

One or more file hosts supporting files of the identified one or morefile types are identified (act 706). These one or more file hosts can bevarious types of file hosts as discussed above, such as otherapplications. The file types supported by the file hosts can beidentified in different manners, such as during a registration processas discussed above.

A user interface including a hosted area is displayed (act 708). Withinthe hosted area, at least one of the one or more file hosts displays aportion of the user interface identifying one or more files that can beselected for retrieval. The file host displaying a portion of the userinterface can change as discussed above. Additionally, as discussedabove, the application can be unaware of which file host is displayingthe user interface in the hosted area, and the file host can tailor theuser interface in the hosted area as that file host desires.

A user selection of one or more files of the at least one file host isreceived (act 710). A user selection of one or more files from each ofone or more of the file hosts can be received as discussed above.

The user selected one or more files are returned to the application (act712). As discussed above, the application can be unaware of from whichof the one or more file hosts the one or more files are selected.

FIG. 8 illustrates another example procedure 800 for implementing thefile access with different file hosts in accordance with one or moreembodiments. Procedure 800 is implemented by a file management module,such as file management module 106. In procedure 800, a file accessrequest is received from an application (act 802). The request can bereceived by the application invoking an API exposed by a broker moduleof the file management module, as discussed above, and can be a requestto save one or more files.

A file type of a file to be saved by the application is identified (act804). This file type can be identified in different manners, such asbeing included as part of the file access request, being provided by auser input, being inherent in the file (e.g., identified by an extensionthat is part of the name of the file, identified as metadata associatedwith the file), and so forth.

One or more file hosts supporting files of the identified file type areidentified (act 806). These one or more file hosts can be various typesof file hosts as discussed above, such as other applications. The filetypes supported by the file hosts can be identified in differentmanners, such as during a registration process as discussed above.

A user interface including a hosted area is displayed (act 808). Withinthe hosted area, at least one of the one or more file hosts displays aportion of the user interface allowing the file to be saved by the atleast one file host. The location where the file is to be saved can beselected by the user via the user interface displayed in the hostedarea, as discussed above. The file host displaying a portion of the userinterface can change as discussed above. Additionally, as discussedabove, the application can be unaware of which file host is displayingthe user interface in the hosted area, and the file host can tailor theuser interface in the hosted area as that file host desires.

CONCLUSION

Various actions such as communicating, receiving, sending, storing,generating, obtaining, and so forth performed by various modules arediscussed herein. It should be noted that the various modules can causesuch actions to be performed. A particular module causing an action tobe performed includes that particular module itself performing theaction, or alternatively that particular module invoking or otherwiseaccessing another component or module that performs the action (orperforms the action in conjunction with that particular module).

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

1-20. (canceled)
 21. A computing device comprising a processor and acomputer-readable storage medium, the computer-readable storage mediumstoring computer instructions causing the processor to performoperations comprising: invoking, by an application running on thecomputing device, an application programming interface (API) to requestaccess to files stored by a remote service provider, wherein the requestto access files via the API comprises: identification of a file type offiles for which access is requested; displaying a user interfaceincluding a hosted area, wherein the hosted area presents user interfaceelements for files stored by the remote service provider that match therequest, wherein the remote service provider is restricted to displayingthe user interface elements for the files within the hosted area;selecting, via the hosted area of the displayed user interface, one ormore of the displayed files stored by the remote service provider thatmatch the request; and retrieving, via the API, the one or more selectedfiles.
 22. The computing device of claim 21, wherein the remote serviceprovider is a photo management service.
 23. The computing device ofclaim 21, wherein the files displayed in the user interface are imagefiles.
 24. The computing device of claim 21, wherein the API supportsselecting a file type of video files and a file type of image files forthe identification of the file type of files for which access isrequested.
 25. The computing device of claim 21, wherein the applicationis unaware of a data model used by the remote service provider.
 26. Thecomputing device of claim 21, wherein the hosted area presents userinterface elements for navigating groupings of files.
 27. The computingdevice of claim 21, the operations further comprising: receiving alocation for saving the retrieved one or more selected files.
 28. Thecomputing device of claim 21, the operations further comprising:invoking, by an application running on the computing device, the API toprovide a user input, wherein the user input provides informationregarding one or more other files stored by the remote service provider.29. A method, implemented by a computing device, the method comprising:invoking, by an application running on the computing device, anapplication programming interface (API) to request access to filesstored by a remote service provider, wherein the request to access filesvia the API comprises: identification of a file type of files for whichaccess is requested; displaying a user interface including a hostedarea, wherein the hosted area presents user interface elements for filesstored by the remote service provider that match the request, whereinthe remote service provider is restricted to displaying the userinterface elements for the files within the hosted area; selecting, viathe hosted area of the displayed user interface, one or more of thedisplayed files stored by the remote service provider that match therequest; and retrieving, via the API, the one or more selected files.30. The method of claim 29, wherein the remote service provider is aphoto management service.
 31. The method of claim 29, wherein the filesdisplayed in the user interface are image files.
 32. The method of claim29, wherein the API supports selecting a file type of video files and afile type of image files for the identification of the file type offiles for which access is requested.
 33. The method of claim 29, whereinthe hosted area presents user interface elements for navigatinggroupings of files.
 34. The method of claim 29, the operations furthercomprising: invoking, by an application running on the computing device,the API to provide a user input, wherein the user input providesinformation regarding one or more other files stored by the remoteservice provider.
 35. A method, implemented by a computing device, themethod comprising: receiving, via an application programming interface(API), a file access request, wherein the file access request isreceived from an application running on the computing device, whereinthe file access request is a request to access files stored by a remoteservice provider, and wherein the file access request comprises:identification of a file type of files for which access is requested;displaying a user interface including a hosted area, wherein the hostedarea presents user interface elements for files stored by the remoteservice provider that match the request, wherein the remote serviceprovider is restricted to displaying the user interface elements for thefiles within the hosted area; receiving a selection, via the hosted areaof the displayed user interface, of one or more of the displayed filesstored by the remote service provider that match the request; andproviding, via the API, the one or more selected files to theapplication.
 36. The method of claim 35, wherein the remote serviceprovider is a photo management service.
 37. The method of claim 35,wherein the files displayed in the user interface are image files. 38.The method of claim 35, wherein the API supports selecting a file typeof video files and a file type of image files for the identification ofthe file type of files for which access is requested.
 39. The method ofclaim 35, wherein the hosted area presents user interface elements fornavigating groupings of files.
 40. The method of claim 35, theoperations further comprising: receiving, via the API, a user input thatprovides information regarding one or more other files stored by theremote service provider.